se.cs.ieu.edu.tr
Course Name | |
Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
---|---|---|---|---|---|
Fall/Spring |
Prerequisites |
| ||||||||
Course Language | |||||||||
Course Type | Elective | ||||||||
Course Level | - | ||||||||
Mode of Delivery | - | ||||||||
Teaching Methods and Techniques of the Course | |||||||||
Course Coordinator | - | ||||||||
Course Lecturer(s) | |||||||||
Assistant(s) | - |
Course Objectives | |
Learning Outcomes | The students who succeeded in this course;
|
Course Description |
| Core Courses | |
Major Area Courses | ||
Supportive Courses | ||
Media and Managment Skills Courses | ||
Transferable Skill Courses |
Week | Subjects | Required Materials |
1 | Fundamentals of Optimization Review | Lecture Notes |
2 | Dissasembly Problems, - Introduction, definitions, classification | Lecture Notes |
3 | Disassembly specific examples definitions, disassembly planning - Presentation | Lecture Notes |
4 | Disassembly Planning - Presentation | Lecture Notes |
5 | Disassembly Scheduling 1/2 - Presentation | Lecture Notes |
6 | Mini test 1 | Lecture Notes |
7 | Disassembly Scheduling - Presentation | Lecture Notes |
8 | Mini Test 2 | Lecture Notes |
9 | Disassembly Heuristics - Presentations | |
10 | Advanced Planning and Scheduing - Lot Sizing and Scheduling - Presentation | Lecture Notes |
11 | Lot Sizing and Scheduling - Presentation | Lecture Notes |
12 | Mini Test 3 / Lot Sizing and Scheduling - Presentation | Lecture Notes |
13 | Lot Sizing and Scheduling - Presentation | Lecture Notes |
14 | Mini Test 4 / Lot Sizing and Scheduling - Presentation | Lecture Notes |
15 | Review and Presentations | Lecture Notes |
16 | Review of the Semester |
Course Notes/Textbooks | |
Suggested Readings/Materials |
Semester Activities | Number | Weigthing |
Participation | 20 | |
Laboratory / Application | ||
Field Work | ||
Quizzes / Studio Critiques | 4 | 20 |
Portfolio | ||
Homework / Assignments | 2 | 10 |
Presentation / Jury | 2 | 20 |
Project | ||
Seminar / Workshop | ||
Oral Exam | ||
Midterm | ||
Final Exam | 1 | 30 |
Total |
Weighting of Semester Activities on the Final Grade | 65 | |
Weighting of End-of-Semester Activities on the Final Grade | 35 | |
Total |
Semester Activities | Number | Duration (Hours) | Workload |
---|---|---|---|
Course Hours (Including exam week: 16 x total hours) | 16 | 3 | 48 |
Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | ||
Study Hours Out of Class | |||
Field Work | |||
Quizzes / Studio Critiques | |||
Portfolio | |||
Homework / Assignments | 2 | 45 | |
Presentation / Jury | |||
Project | |||
Seminar / Workshop | |||
Oral Exam | |||
Midterms | 1 | 12 | |
Final Exams | 1 | 15 | |
Total | 165 |
# | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
1 | Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute | X | ||||
2 | Be able to design and analyze software at component, subsystem, and software architecture level | |||||
3 | Be able to develop software by coding, verifying, doing unit testing and debugging | |||||
4 | Be able to verify software by testing its behaviour, execution conditions, and expected results | |||||
5 | Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation | |||||
6 | Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically | |||||
7 | To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning | |||||
8 | Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes | |||||
9 | Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance | |||||
10 | To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software | |||||
11 | To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering | X | ||||
12 | Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering | |||||
13 | Be able to use a foreign language to follow related field publications and communicate with colleagues | X |
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest